-
Notifications
You must be signed in to change notification settings - Fork 684
feat(telemetry): add IAM telemetry #7830
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: feature/flare-mega
Are you sure you want to change the base?
Conversation
|
if (!AuthUtil.instance.isSsoSession()) { | ||
telemetry.amazonq_messageResponseError.emit({ | ||
result: 'Failed', | ||
cwsprChatConversationType: 'Chat', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we name this to inlineChat instead of generic Chat ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only reason I didn't change that is in aws-toolkit-common, cwprChatConversationType is defined as such:
{
"name": "cwsprChatConversationType",
"type": "string",
"allowedValues": [
"Chat",
"Assign",
"Transform",
"AgenticChat",
"AgenticChatWithToolUse"
],
"description": "Identifies the type of conversation"
},
Chat might be the most suitable value here. If I can make a PR to change this type in commonDefinition, I will add inlineChat and change the code here as well.
6b7a928
to
cd42ede
Compare
…scode into feature/telemetry
505cd41
to
e68c63c
Compare
Problem
IAM credentials does not fit into current SSO telemetry metrics
Solution
Add IAM specific telemetry metric emission.